Version: 7.7

Process Managament

When reconfiguring or troubleshooting Resolve Actions Pro, you might need to start, stop, restart, or check the status of the components' OS processes.

Script Location

Use the scripts located under <intallation-path>/bin/ on your Actions Pro machine(s) to manage Actions Pro components.

Starting Components

To start one or more components, use the run.sh script:

To start individual components:
```
./run.sh <component-name1> [<component-name2>]
```
Where <component-nameN> is one of rsmgmt, rssearch, rsview, rscontrol, rsremote, rssync, kibana, logstash, rslog, rsmq.
To start all components:
```
./run.sh all
```

Stopping Components

To stop one or more components, use the stop.sh script:

To stop individual components:
```
./stop.sh <component-name1> [<component-name2>]
```
Where <component-nameN> is one of rsmgmt, rssearch, rsview, rscontrol, rsremote, rssync, kibana, logstash, rslog, rsmq.
To stop all components:
```
./stop.sh all
```
To forcefully stop a component, add the -k option to the command. It attempts to stop the component gracefully; if unsuccessful, it stops the process forcefully.
```
./stop.sh -k <component-name1> [<component-name2>]
./stop.sh -k all
```

Restarting Components

The restart command first stops the process and then starts it again.

To restart individual components:
```
./restart.sh <component-name1> [<component-name2>]
```
Where <component-nameN> is one of rsmgmt, rssearch, rsview, rscontrol, rsremote, rssync, kibana, logstash, rslog, rsmq.
To restart all components:
```
./restart.sh all
```

Checking Component Status

The status script lists the running state of Actions Pro components managed through the scripts in the bin directory. The script is also the easiest way to find the PID of a component to use with OS commands such as top or kill.

To check the status of individual components:
```
./status.sh <component-name1> [<component-name2>]
```
Where <component-nameN> is one of rsmgmt, rssearch, rsview, rscontrol, rsremote, rssync, kibana, logstash, rslog, rsmq.
To check the status of all components:
```
./status.sh
```

The output will resemble the following:

КIBANA: UP PID: 99129
LOGSTASH: UP PID: 105487
RSCONTROL: UP PID: 114849
RSLOG: UP PID: 105556
RSMGMT: UP PID: 105328
RSMQ: UP PID: 96786
RSREMOTE: UP PID: 114804
RSSEARCH: UP PID: 98259
RSSync: DOWN
RSVIEW: UP PID: 114910

Component Names

The scripts in bin manage all Actions Pro components that run as OS processes. RSConsole does not require a process and is excluded.

The scripts refer to the components using the following names:

Script Naming	Full Component Name
`rsmgmt`	RSMgmt
`rssearch`	RSSearch (Elasticsearch)
`rsview`	RSView
`rscontrol`	RSControl
`rsremote`	RSRemote
`rssync`	RSSync
`kibana`	Kibana
`logstash`	Logstash
`rslog`	RSLog
`rsmq`	RSMQ (RabbitMQ)

Script Location​

Starting Components​

Stopping Components​

Restarting Components​

Checking Component Status​

Component Names​